home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: OS features
- Date: 2 Feb 1996 20:29:02 +0100
- Organization: dis-
- Message-ID: <4etolu$3mu@serpens.rhein.de>
- References: <DLAA61.2us@inter.NL.net> <4dh2dm$jui@serpens.rhein.de> <1292.6592T166T2158@algonet.se> <4do01q$fmc@serpens.rhein.de> <19960120.7B57BE0.122A3@asd01-04.dial.xs4all.nl> <4dtg0e$1j7@serpens.rhein.de> <19960123.7B89070.14DD@asd07-10.dial.xs4all.nl> <4e384c$13j@serpens.rhein.de> <19960202.7B12650.388B@asd05-06.dial.xs4all.nl>
- NNTP-Posting-Host: serpens.rhein.de
-
- jtv@xs4all.nl (Jeroen T. Vermeulen) writes:
-
- >As we're talking about implementing a special-purpose device driver here anyway,
- >I don't see a reason (yet) why it can't be programmed so as to run in a single
- >task.
-
- So you are going to write two drivers for every hardware ?
-
- >Would this work for a single-level VM system (or the top level of a multi-level
- >system)?
-
- What is a multi-level VM system ?
-
- >That depends on implementation, I guess. There must never be "circular page
- >fault" on such memory (and excessive copying is probably best avoided).
-
- I guess the easiest method is to lock the whole driver and associated memory.
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-